Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat(network): include PKs in the version str #1843

Merged

Conversation

maqi
Copy link
Member

@maqi maqi commented Jun 5, 2024

Description

Include PKs in the version string, hence node/client using mismatched keys will be rejected by the network.

Related Issue

Fixes #<issue_number> (if applicable).

Type of Change

Please mark the types of changes made in this pull request.

  • New feature (non-breaking change which adds functionality)

@joshuef
Copy link
Contributor

joshuef commented Jun 17, 2024

@maqi this needs a proper BREAKING CHANGE: not in the commit message. With that we can get this into main.

@maqi maqi removed the Discussion label Jun 17, 2024
@maqi maqi force-pushed the include_key_check_in_identify_protocol branch 2 times, most recently from 4be629a to c5ee933 Compare June 17, 2024 10:39
BREAKING CHANGE: this will make new launched network incompatible with
old client or node.
@maqi maqi force-pushed the include_key_check_in_identify_protocol branch from c5ee933 to 0825217 Compare June 17, 2024 12:22
@RolandSherwin RolandSherwin added this pull request to the merge queue Jul 2, 2024
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Jul 2, 2024
@RolandSherwin RolandSherwin added this pull request to the merge queue Jul 2, 2024
@jacderida jacderida removed this pull request from the merge queue due to a manual request Jul 2, 2024
@jacderida jacderida merged commit 19fb1cb into maidsafe:main Jul 2, 2024
41 of 42 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants